Graphical user interface for viewing or editing an executable block diagram model

ABSTRACT

In one embodiment, a method for displaying elements of an attribute in an executable block diagram model is provided. The method may include displaying an executable block diagram model in a first window and receiving a first input from an input device, wherein the first input associates with a first parameter of a block diagram modeling component in the executable block diagram model, the first parameter is represented in the executable block diagram model by a first graphical affordances. The method may include triggering the display of a value of a first parameter in a first user interface widget in the first window.

BACKGROUND

In an executable block diagram model, there may be multiple blocks andlines connecting the blocks. Dialog boxes are often used to view and/oredit parameters used in the executable block diagram model. Conventionalconfigurations may require that a user switch focus between the modelwindow and the dialog box windows for viewing and/or editing parametervalues.

SUMMARY

In one embodiment, a computer readable medium holding computerexecutable instructions for displaying one or more attributes associatedwith one of one or more block diagram modeling components of anexecutable block diagram model may be provided. The medium may includeinstructions for displaying an executable block diagram model in a firstwindow, the executable block diagram model comprising a first blockdiagram modeling component having a first attribute. The first blockdiagram modeling component may be associated with a first graphicalaffordance. The first block diagram modeling component may be displayedwith the first graphical affordance. The first graphical affordance maybe activated. The medium may further include instructions for displayinga first widget in response to activating the first graphical affordance,the first widget displaying one or more attribute values associated withthe first block diagram modeling component.

Yet in another embodiment, a computer readable medium holding computerexecutable instructions for causing a computing device to display one ormore attributes associated with one or more block diagram modelingcomponents of an executable block diagram model, where at least one ofthe one or more attributes has one or more attribute values may beprovided. The medium may include instructions for displaying anexecutable block diagram model in a first window, where the executableblock diagram model comprises a first block diagram modeling componentthat includes a first attribute having one or more attribute values. Oneor more hotspot regions around the first block diagram modelingcomponent may be identified. The identifying may include associating oneof the one or more hotspot regions with the first attribute. Theidentifying may further include associating another of the one or morehotspot regions with a second attribute when a second attribute isassociated with the first block diagram modeling component. The mediummay also include instructions for receiving a first input for the firstattribute or the second attribute, where the first input modifies one ormore attribute values of the first attribute or the second attribute.The one or more attribute values associated with the first attribute orthe one or more attribute values associated with the second attributemay be displayed via a first widget in the first window, where thedisplaying provides updated information about the first block diagrammodeling component or the executable block diagram model.

Still in another embodiment, a computer readable medium holding computerexecutable instructions for searching one or more attributes associatedwith one or more block diagram modeling components of an executableblock diagram model may be provided. The medium may hold instructionsfor displaying an executable block diagram model in a first window,wherein the executable block diagram model comprises one or more blockdiagram modeling components having one or more attributes, the one ormore attributes having one or more attribute values. The medium mayfurther hold instructions for displaying a search tool in the firstwindow, wherein the search tool includes a category option thatcomprises a search category or a text field for receiving a searchstring, the search string relating to one or more attribute values. Theattributes of the executable block diagram model may be searched tomatch the search category or the search string with the one or moreattribute values. One or more block diagram modeling components havingone or more attributes with attribute values matching to the searchcategory or the search string may be located. The one or more locatedblock diagram modeling components may be displayed in the first window.

In another embodiment, a computer readable medium holding computerexecutable instructions for viewing different layers of detail of one ormore block diagram modeling components of an executable block diagrammodel may be provided. The medium may include instructions fordisplaying an executable block diagram model with one or more blockdiagram modeling components, the one or more block diagram modelingcomponents having at least a normal viewing mode. The executable blockdiagram model may be navigated using a multi-level detail viewer. One ofthe one or more block diagram modeling components may be selected bypositioning the multi-level detail viewer on the selected block diagrammodeling component. The medium may also include instructions fordisplaying a first level of detail of the selected block diagrammodeling component; the first level of detail illustrating one or moreattributes of the selected block diagram modeling component. The one ormore block diagram modeling components may be displayed in the normalviewing mode when the one or more block diagram modeling components arenot selected.

In still another embodiment a system for displaying one or moreattribute values of one or more attributes of a block diagram modelingcomponent in an executable block diagram model is provided. The systemmay include a display device that displays an executable block diagrammodel having one or more block diagram modeling components in a window,wherein the one or more block diagram modeling components have one ormore attributes and a model editor that associates one or more blockdiagram modeling components or regions around the one or more graphicalcomponents with one or more graphical affordances. The system mayfurther include an attribute value viewer that in response to activatingthe one or more graphical affordances, displays a first widget forillustrating one or more attribute values of a first attributeassociated with a first block diagram modeling component and an inputdevice for entering input to modify the one or more attribute valuesdisplayed on the first widget. The system may also include an updatinglogic that updates the display of the block diagram with the inputentered using the input device.

BRIEF DESCRIPTION OF THE FIGURES

The foregoing and other aspects, features, and advantages of theinvention will become more apparent and may be better understood byreferring to the following description taken in conjunction with theaccompanying drawings, in which:

FIG. 1A is a block diagram of a computing device suitable for practicingan exemplary embodiment;

FIG. 1B is a block diagram of a modeling environment suitable forpracticing an exemplary embodiment;

FIG. 2A illustrates an exemplary user interface widget that displaysvalues of a signal parameter of an exemplary model;

FIG. 2B illustrates how the user interface widget can be repositioned inthe exemplary model in FIG. 2A;

FIG. 2C illustrates an exemplary user interface widget that displays ahistory of values of a block parameter;

FIG. 3A illustrates exemplary user interface widgets that display blockparameters and their values;

FIG. 3B illustrates how a value of a block parameter can be modifiedusing a pointing device in an exemplary embodiment;

FIG. 3C illustrates how a value of a block parameter can be modifiedusing a keyboard in an exemplary embodiment;

FIG. 3D illustrates how a block parameter value can be made selectivelyvisible and how the user interface widget showing the parameter valuecan be repositioned in an exemplary embodiment;

FIG. 3E illustrates an exemplary user interface widget that may be usedto display a property of a block diagram modeling component;

FIG. 3F illustrates how different user interface widgets may be usedwith a block diagram modeling component in an exemplary embodiment;

FIG. 3G illustrates how a hotspot can be created and how the hotspot canbe customized in one exemplary embodiment;

FIG. 3H illustrates an exemplary user interface that may be used tochange an appearance and position of a hotspot;

FIG. 3I illustrates the use of an image to customize the appearance of ahotspot in one exemplary embodiment;

FIG. 3J illustrates how the shape and position of the hotspot may becustomized in one exemplary embodiment;

FIG. 3K illustrates how a plot of a function can be used as theappearance of a hotspot in one exemplary embodiment;

FIG. 4A illustrates the use of an exemplary editable pop-up table todisplay block parameter values and the use of a drop-down box to edit ablock parameter value;

FIG. 4B illustrates the use of a text field in the exemplary editablepop-up table in FIG. 4A to edit a block parameter value;

FIG. 4C illustrates the use of an exemplary user interface that does notuse a table to display block parameter values in one exemplaryembodiment;

FIG. 5A illustrates a bar that allows viewing and editing of blockparameter values in an exemplary graphical user interface;

FIG. 5B illustrates a search bar for searching for a parameter with aspecific value in an exemplary graphical user interface;

FIG. 5C illustrates an exemplary output of a search result in oneexemplary embodiment;

FIG. 5D illustrates an exemplary output of a search result in the statusbar in one exemplary embodiment;

FIG. 6A illustrates a flowchart depicting exemplary processing that canbe used to display and/or edit a parameter value;

FIG. 6B illustrates additional processing with respect to FIG. 6A thatmay be performed to practice one exemplary embodiment;

FIG. 7 illustrates a flowchart depicting exemplary processing that canbe used to search for a parameter according to one exemplary embodiment;

FIG. 8A illustrates an exemplary executable block diagram model that isreferenced in FIGS. 8B to 8H for describing exemplary graphical userinterfaces for viewing a specified level of detail of a block diagrammodeling component;

FIG. 8B illustrates an exemplary graphical user interface for viewingdifferent levels of detail of a block diagram modeling component;

FIG. 8C illustrates another exemplary graphical user interface forviewing different levels of detail of a block diagram modelingcomponent;

FIG. 8D illustrates an exemplary algorithm detail of a block diagrammodeling component;

FIG. 8E illustrates an exemplary generated code detail of a blockdiagram modeling component;

FIG. 8F illustrates an exemplary graph detail of a block diagrammodeling component;

FIG. 8G illustrates an exemplary data detail of a block diagram modelingcomponent;

FIG. 8H illustrates an exemplary subsystem detail of a block diagrammodeling component;

FIG. 9A illustrates an exemplary statechart that is referenced in FIGS.9B and 9C for describing exemplary graphical user interfaces for viewinga specified level of detail of a statechart component;

FIG. 9B illustrates an exemplary graphical user interface for viewingdifferent levels of detail of a statechart component;

FIG. 9C illustrates a close-up view of the statechart component;

FIG. 10A illustrates an exemplary detail of a composite signal;

FIG. 10B illustrates another exemplary detail of a composite signal;

FIG. 11A illustrates an exemplary graphical user interface that may beused to find issues in an executable block diagram model;

FIG. 11B illustrates an exemplary issue that may be displayed in theexemplary graphical user interface;

FIG. 11C illustrates how a level of detail may be displayed to show theexemplary issue in the executable block diagram model; and

FIG. 12 illustrates a flow chart depicting exemplary processing thatallows use a multi-level detail viewer to be used in one exemplaryembodiment.

DETAILED DESCRIPTION

Exemplary embodiments may provide techniques, computer-based mediums,systems and/or devices for viewing and/or editing of attributes ofcomponents of an executable block diagram model. The attributes may be,but are not limited to, for example, parameters, subsystem elements,representations generated via a scripting language, or generated code.In one embodiment, a user can view and edit attributes in the samewindow where the executable block diagram model is displayed. Hence, auser does not need to switch between windows to view and/or editattributes.

A dynamic system (either natural or man-made) is a system whose responseat any given time is a function of its input stimuli, its current state,and the current time. Physical dynamic systems include, for example, afalling body, the rotation of the earth, bio-mechanical systems(muscles, joints, etc.), bio-chemical systems (gene expression, proteinpathways), weather and climate pattern systems, etc. Examples ofman-made or engineered dynamic systems include: a bouncing ball, aspring with a mass tied on an end, automobiles, airplanes, controlsystems in major appliances, communication networks, audio signalprocessing, nuclear reactors, a stock market, etc.

An executable block diagram model of a dynamic system is representedschematically as a collection of blocks interconnected by lines thatrepresent signals. A signal represents the input and output of a dynamicsystem. Each block represents an elemental dynamic system. A lineemanating at one block and terminating at another signifies that theoutput of the first block is an input to the second block. Each distinctinput or output on a block is referred to as a port. Signals correspondto the time-varying quantities represented by each line connection andare assumed to have values at each time instant. The source block of asignal writes to the signal at a given time instant when its systemequations are solved. The destination blocks of this signal read fromthe signal when their system equations are being solved. Those skilledin the art will recognize that the term “blocks” does not referexclusively to elemental dynamic systems but may also include othermodeling elements that aid in readability and modularity of blockdiagrams.

In an embodiment, the user interface widgets can be used to display theattributes. These widgets can be repositioned by a user request (e.g.,such as a drag and drop function performed by the user). In anotherembodiment, the user interface widgets may be moved to another window orto the desktop. In one embodiment, a user can determine if a userinterface widget, such as a tooltip, should be persistently visible inthe executable block diagram model, and the user can also determine thelayout of the user interface widget with respect to the executable blockdiagram model. Some embodiments may also provide techniques and/ordevices for searching for a specific parameter type and value in theexecutable block diagram model.

Other embodiments may provide techniques, computer-readable mediums,systems, and/or devices for providing a multi-level detail viewer fordisplaying different levels of detail for a block diagram modelingcomponent. For example, different levels of detail may be displayed as auser browses/navigates in an executable block diagram model. In oneembodiment, different types of block diagram modeling components mayhave different levels of detail. In one embodiment, the specified levelof detail may be displayed directly on top of the corresponding blockdiagram modeling component. In another embodiment, the specified levelof detail may be displayed in another window that is embedded in themodel window. The model window displays the executable block diagrammodel. In one embodiment, a property/setting displayed in the specifiedlevel of detail may be modified.

FIG. 1A depicts components suitable for practicing exemplaryembodiments. The computing device 102 may be any computer device and/orsystem, such as a workstation, desktop computer, server, laptop,handheld computer or other form of computing or telecommunicationsdevice that is capable of communication with another device/system andthat has sufficient processor power and/or memory to perform theoperations described herein.

The computing device 102 can be running substantially any operatingsystem such as a version of the Microsoft® Windows® operating systems,Unix operating system, Linux operating systems, MacOS® operating system,etc. Implementations of computing device 102 may further operate anembedded operating system, a real-time operating system, an open sourceoperating system, a proprietary operating system, an operating systemfor mobile computing devices, and/or another type of operating systemcapable of running on computing device 102 and/or performing operationsdescribed herein.

Other computing resources, such as Field Programming Gate Array (FPGA),Application Specific Integrated Circuit (ASIC), Application SpecificInstruction Processor (ASIP), Digital Signal Processor (DSP), graphicsprocessing unit (GPU), and General Purpose Processor (GPP), may also beused for executing code and/or software. A hardware accelerator 119,such as implemented in an ASIC, FPGA, or the like, can additionally beused to increase a processing rate of the computing device 102.

Computing device 102 includes memory 106, on which software according toone embodiment of the present invention may be stored, processor(s) 104for executing software stored in the memory 106, and other programs forcontrolling system hardware.

The memory 106 may include among other things a computer system memoryor random access memory (RAM), such as dynamic random access memory(DRAM), static random access memory (SRAM), Magnetoresistive RandomAccess Memory (MRAM), extended data out random access memory (EDO RAM),etc. A user may interact with the computing device 102 through akeyboard 110, a pointing device 112, and/or a visual display device 114such as a computer monitor, which may include a user interface 115. Theuser interface 115 enables the user to interact with the modelingenvironment 120 through the computing device 102. The user may send aninput to manipulate an element of the modeling environment 120 using theuser interface 115. The user interface 115 may also display the effectsof the user input. Other input devices, such as accelerometer andgyroscope based input devices, active whiteboards, cameras, microphones,neuro interface devices, may also be used with computing device 102.

The computing device 102 may further include a storage device 108, suchas a hard-drive, compact disc-read-only memory (CD-ROM), or othercomputer readable medium, for storing an operating system 116 and otherrelated software, and for storing the modeling environment 120.Additionally, the operating system 116 and modeling environment 120 maybe run from a computer readable media, such as, for example, KNOPPIX®, abootable CD for GNU/Linux.

FIG. 1B depicts the modeling environment 120 that includes a modeleditor 126 for creating and/or editing an executable block diagrammodel. In one embodiment, modeling environment 120 may include aparameter value viewer 122 for viewing and optionally editing parametervalues in an executable block diagram model. In one embodiment, theparameters may be associated with a block diagram modeling component ora portion of an executable block diagram model (e.g., a subsystem).Alternatively, the parameters may be global parameters that do notassociate with any particular block diagram modeling component, but withthe executable block diagram model as a whole. Modeling environment 120may also include search tool 124 for searching a specific parameter witha specific value.

In one embodiment, model editor 126 provides graphical user interfacewidgets to display parameter values. The graphical user interfacewidgets may be repositioned in the executable block diagram model, ormoved to a different window, or moved to a desktop. In one embodimentspecific to Microsoft® Windows®, graphical user interface widgets may beplaced on the desktop using the Active Desktop interface provided by theMicrosoft® Windows® Shell Application Programming Interface (API). Inanother embodiment, graphical user interface widgets may be moved from afirst window to a second window using dynamic data exchange or theComponent Object Model (COM) interface. For example, the dynamic dataexchange technique allows different Windows® applications to share dataor send commands to one another.

In another embodiment, a multi-level detail viewer 128 may be providedin modeling environment 120 so that different levels of detail of ablock diagram modeling component may be displayed. In one embodiment,one or more details of a block diagram modeling component arecategorized into a certain level of detail. For different types of blockdiagram modeling components, different types of level of detail anddifferent quantities of level of detail may be provided. For example, inone embodiment, modeling environment 120 may have a set of predeterminedlevels of detail for a block diagram modeling component. Modelingenvironment 120 may display relevant information for a selected level ofdetail for the corresponding block diagram modeling component based on aselected level of detail.

Parameter value viewer 122, search tool 124, and multi-level detailviewer 128 can be adapted to be included as part of the modelingenvironment 120, or they can each be a stand-alone application, module,script, plug-in, or program that responds to calls from the modelingenvironment 120.

Additionally, the computing device 102 may include a network interface118 to interface to a Local Area Network (LAN), Wide Area Network (WAN)or the Internet through a variety of connection types including, but notlimited to, standard telephone lines, LAN or WAN links (e.g., 802.11,802.16, T1, T3, 56 kb, X.25), broadband connections (e.g., IntegratedServices Digital Network (ISDN), Frame Relay, asynchronous transfer mode(ATM)), wireless connections, etc., or some combination of any or all ofthe above.

The network interface 118 may include a built-in network adapter,network interface card (NIC), Personal Computer Memory CardInternational Association (PCMCIA) network card, card bus networkadapter, wireless network adapter, Universal Serial Bus (USB) networkadapter, modem or any other device suitable for interfacing thecomputing device 102 to any type of network capable of communication andperforming operations described herein.

Virtualization can be employed in computing device 102 so thatinfrastructure and/or resources in computing device 102 can be shared.Virtualized processors may also be used with modeling environment 120and/or other software in storage 108. A software referred as a virtualmachine may be used to create a virtualized environment between thecomputing device 102 and the infrastructure and/or resources of thecomputing device 102. A virtual machine 103 can be provided to handle aprocess running on multiple processors so that the process appears to beusing only one computing resource rather than multiple computingresources. Multiple virtual machines can also be used with oneprocessor.

FIG. 2A illustrates use of an exemplary user interface widget forviewing values of a signal parameter in an exemplary model. Executableblock diagram model 200 is an exemplary model that can be implementedusing a modeling environment. Other models that can be used withexemplary techniques described herein can be implemented in other typesof modeling environments. In one embodiment, executable block diagrammodel 200 may be an executable model includes multiple blocks and/orsignals. A user can choose to view values of signal 202 by selecting thesignal 202. A selection can be made, for example, by clicking on thesignal 202 or hovering over the signal 202 with a cursor.

A signal, as used herein, represents a set of values. For example, asignal may be a set of values that can be stored, read from storage,manipulated, sent from a source to a destination, etc. For example, asignal may be associated with a path (e.g., a connection line) in anexecutable block diagram model. The path may indicate a source locationfor the signal and a destination for the signal. In one implementation,the signal may be read from the source location and stored at thedestination. In another implementation, the signal may propagate fromthe source location to the destination along the path. Signals that canbe used with exemplary embodiments may take on different values as amodel executes. Signals may have attributes, such as dimensionality,data type, sample rate, etc.

When signal 202 is selected, a user interface widget 206, such as atooltip or balloon help, appears and displays information about thesignal parameter values of signal 202. For example, signal 202 may be agraphical affordance that acts as a control that may trigger the displayof widget 206. A widget is an interface element that a computer userinteracts with, such as a window, a text box, or the like. A graphicalaffordance is used to indicate to the user that when activated, thegraphical affordance will result in an action. The graphical affordanceindicates an ability to control or trigger an action. Widget 206displays signal parameter values at a given time during the simulationof the executable block diagram model 200. Scroll bar 214 is provided toallow a user to scroll through the history of signal parameter valuesfor signal 202. The scroll bar 214 helps the user to see the informationthat does not fit in the display area of the widget 206. The scroll bar214 may take other forms such as a slider, a dial or the like. Userinterface widget 208 displays signal parameter values for signal 204.Widgets 206 and 208 may be resized at a user's request, such as, forexample, by dragging and dropping the borders of the widget.

Signal 204 is a graphical affordance that acts as a control that maytrigger the display of widget 208. Widget 208 may also include scrollbar 216 for viewing different signal parameter values at differentsimulation times. Both widgets 206 and 208 are embedded in the modelwindow so that a user does not need to switch windows to view signalparameter values. Exemplary implementations allow a user to viewparameter values in the same window as the model.

Widgets 206 and 208 may utilize references or pointers to memory 106 orstorage 108 where the values of signals are stored so that widgets 206and 208 can reflect any changes in the respective signal values.Alternatively, modeling environment 120 may supply the signal values forwidgets 206 and 208 for display. The positioning, size, elements, anddisplay time of the widgets 206 and 208 may be controlled by themodeling environment 120. Modeling environment 120 may also provideoptions for a user to customize the positioning, size, elements, anddisplay time of the widgets 206 and 208.

The parameter value viewer 122 may provide menus (e.g., right-clickmenus) for some or all of the widgets 206-208. For example, widget 206can have a right-click menu 210 that allows a user the option to plotsignal values in a figure, to save the value signals to a workspace orto change logging options.

Parameter value viewer 122 can also allow widgets to have icons otherthan a scroll bar 214. For example, widget 208 can have a plot icon 218.When a user clicks on the plot icon 218, a window appears to display aplot 212 of the signal parameter values. Plot 212 may be drawn byfeeding signal values and their corresponding time data into a plotfunction in a programming software. The plot 212 may be a dynamic plotreflecting simulation data of the signal 204 as the simulationprogresses. In another example, a connection icon may be provided inwidget 208 to connect signal 204 to a scope block in a modelingenvironment for a user to view how the signal value changes as afunction of time.

Furthermore, an option can be provided, such as via a button, to allowsignal values of signal 204 to be exported or saved into a workspace sothat a user can manipulate the signal data as desired in thecorresponding programming environment. Widgets 206 and 208 may includeadditional information, such as the name of the corresponding signal,the source of the signal, the destination of the signal, etc. Widgets206 and 208 may also include less information than what is illustratedin FIG. 2A. Widgets 206 and 208 may include any type of text, graphics,or hyperlinks to display or manipulate information related tocorresponding graphical affordances (i.e. signals 202 and 204respectively in this case).

FIG. 2B illustrates how a widget can be repositioned in the model 200.In this example, the widget 206 is repositioned relative to its positionin FIG. 2A. Once a widget appears in the executable block diagram model200, a user can move the widget around in the executable block diagrammodel 200. For example, widget 206 can be moved away from signal 202 andto a side of the executable block diagram model 200. In one embodimentof the present invention, widget 206 can have an “x” at the upper righthand corner of the widget, so that a user can determine when the widgetshould no longer be present in the model 200 by selecting the “x” with apointing device. In one embodiment, a widget may maintain a relativeposition to its corresponding block diagram modeling component, such asa signal, so that the widget moves corresponding with the movement ofthe corresponding graphical model component.

FIG. 2C illustrates another exemplary user interface widget that can beused to view a history of values of a block parameter. When a userselects block 220, a user interface widget 222 can appear and show thename of the block with its current value 1 at time T7 and previousvalues 0.975 at time T0 and 0.950 at time T5. The widget 222 may displaydynamic data. In the dynamic state, the widget 222 may display theblock's value at time T10 while the previous values will show the valuesat time T0, T5 and T7. An “x” may also be provided at the upper righthand corner of the widget 222 so that a user can make the widget 222disappear when desired. One of ordinary skill in the art will appreciatethat the present invention is not limited to the specific GUI widgetsillustrated or mentioned herein and any suitable GUI widget may be usedin the present invention for displaying signal values and/or blockparameters.

FIG. 3A illustrates how block parameters and their values can bedisplayed in an exemplary embodiment. Block 300 can be used as a part ofa model, and when block 300 is not selected, no parameter for the blockis displayed. Block 300 can be selected by placing an arrow cursor 302over block 300 and hovering for a predetermined period of time or byclicking on the block 300 with a pointing device.

Once block 300 is selected, one or more hotspots may be displayed in themodel window. As used herein, a screen hotspot (hotspot) is referred toas a region of a block diagram modeling component, an icon, a pop-updisplay or other graphical affordances. A hotspot may be representedwithout using a special icon to indicate its location. The hotspot maybe visually distinct or a user action may reveal the hotspot, forexample by changing the shape of the arrow cursor. Block 300 has hotspot304, hotspot 306, and hotspot 308. In one embodiment, all hotspots aredisplayed when block 300 is selected. In another embodiment, onlycertain hotspots are displayed. In still another embodiment, brokenlines (e.g., dashed, dotted, etc.) may be used to illustrate thelocation and/or region of the hotspot, or different shades or color mayalso be used to illustrate the location and/or region of the hotspot.One of ordinary skill in the art will appreciate that there are manydifferent ways to graphically represent a hotspot.

In an exemplary embodiment, a hotspot may act as a control that triggersthe display of an associated user interface widget. For example, whenarrow cursor 302 is navigated into a hotspot, a user interface widget,such as a tooltip, can appear and may display the associated parametername and/or value. In one embodiment, when arrow cursor 302 is navigatedover a hotspot, the border of the hotspot area may change appearance,such as becoming a solid red line, to provide feedback to the user thatthe arrow cursor 302 has entered a region that can activate the hotspot.Alternatively, the solid red line may appear when the arrow cursor 302moves within the block outline or other regions that has a relation tothe hotspot. As the arrow cursor 302 hovers over the hotspot area, thehovering may trigger the display of the corresponding GUI widget, suchas a tooltip. The user interface widget may disappear once the arrowcursor 302 moves away from the hotspot and moves out a region of thehotspot that triggers the display of the user interface widget.

When arrow cursor 302 is navigated to the hotspot 308, user interfacewidget 318 may be displayed to show the parameter name as “Operator” andparameter value as “AND”. When the arrow cursor 302 is on the hotspot306, user interface widget 316 indicates the name of the associatedparameter is “Num of ports” and the value of the associated parameter is“2”. As the arrow cursor 302 moves into hotspot 304, a user interfacewidget 314 appears and displays the associated parameter name “Sampletime” and value “−1”.

In one embodiment, a user can view parameter values as he/she navigatesthrough an executable block diagram model. The user interface widgetappears in the same window as the executable block diagram model. Theparameter value is displayed on a separate window, such as a dialog boxwindow. In one embodiment, each hotspot has a 1 to 1 relationship withthe associated parameter or can alternatively be associated with a setof parameters.

FIG. 3B illustrates how a value of a block parameter can be modifiedusing a pointing device. In order to modify a parameter of a block, theblock is selected. Once the block is selected, the hotspot thatcorresponds to the parameter that a user wishes to edit is thenselected. In the case of FIG. 3B, hotspot 308 is selected. Hotspot 308can be selected, for example, by single-clicking on the hotspot 308. Oneof ordinary skill in the art will appreciate that other implementationsof selection can also be used to practice the present invention.

When hotspot 308 is selected, a user interface widget 328 appears toshow the associated parameter name and value. User interface widget 328may provide a drop-down list for changing the associated parametervalue. A user can use a pointing device to move the cursor 302 toactivate the drop-down list and choose a new value from the optionsprovided in the drop-down list. In FIG. 3B, a new value of “OR” isselected and the drop-down list returns to its inactive state and theappearance of the user interface widget 308 is updated to reflect thechange (i.e. showing “OR” instead of “AND”).

A user interface widget can include any type or number of graphical userinterface elements that can allow a user to modify a parameter value.Although a drop-down list is shown in FIG. 3B as the user interfaceelement for a user to edit a parameter value, one of ordinary skill inthe art will appreciate that the present invention is not limited to aspecific kind of graphical user interface widget to edit a parametervalue.

FIG. 3C illustrates how a value of a block parameter can be modifiedusing a keyboard. As mentioned earlier, a letter from the parameter namemay be used as a hotkey that is associated with the parameter. A hotkeyrefers to a single key or a sequence and/or combination of keys that areused to associate with a parameter of a selected block diagram modelingcomponent. Pressing parameter hotkeys when the block is selected willhighlight and start the editing of the related parameter and/orhotspots.

Referring back to FIG. 3A, user interface widget 314 shows thatkeystroke “t” is the hotkey associated with the sample time parameter bybeing shown in bold. Widget 316 shows that key “p” is the hotkeyassociated with the number of ports parameter, whereas widget 318 showsthat “O” is the hotkey associated with the operator parameter. In a caseinsensitive implementation, a single key “o” can be the hotkeyassociated with the operator parameter, while in a case sensitiveimplementation, key “SHIFT+o” or other methods of producing an uppercase “O” can be used as the hotkey.

In one embodiment, the letter or symbol representing the hotkey can berecognized in the displayed parameter name in the widget so that a userdoes not need to look up or search for a hotkey that is related to aparameter of a selected block diagram modeling component. In FIGS. 3A to3C, the letter representing the hotkey has a bold font. In anotherembodiment, the letter(s) and/or symbol(s) representing the hotkey canhave a different font, a different color, underlined, highlighted, adifferent background color, etc. There are many ways to make theletter(s) and/or symbol(s) that represents the hotkey recognizable inthe displayed parameter name or the component icon and the presentinvention is not limited to the exemplary embodiments.

Referring back to FIG. 3C, once a block diagram modeling component isselected, pressing a hotkey may display the corresponding user interfacewidget that displays the name and value of the associated parameter. InFIG. 3C, key “p” is pressed to initiate editing of the parameter valuefield in widget 326. A vertical line cursor 322 is automaticallypresented in the text field in widget 326. One of ordinary skill in theart will appreciate that the specific cursors used in the illustrativeembodiments are not meant to limit the scope of the present inventionand other cursors may also be used with the present invention.Alternatively, the text field may be displayed without a visualappearance such as a cursor. The user may edit the parameter by simplyentering the new parameter in the text field provided in proximity ofthe widget 326.

After pressing the key “p”, the value of the parameter number of portsis changed to 3 by pressing key “3”. By pressing “Enter” key on akeyboard, the parameter value is updated and the appearance of hotspot306 is updated (to show there are three ports instead of two). In otherwords, once block 300 is selected, a user can press “p,” “3,” and“Enter” keys in sequence to change a parameter value and the change maybe reflected in the appearance of the hotspot. In one embodiment, userscan view and/or modify parameter values in an executable block diagrammodel quickly with the use of hotkeys.

FIG. 3D illustrates how a block parameter value can be made selectivelyvisible and how the user interface widget showing the parameter valuecan be repositioned in one exemplary embodiment. In one embodiment, if aparameter is not made selectively visible, then the widget displayingthe parameter name and value disappears as the cursor 302 moves out aregion that activates the display of the widget associated with theparameter. In another embodiment, if a parameter is not made selectivelyvisible, the widget displaying the parameter name and value maydisappear as the cursor 302 moves into a region that deactivates thedisplay of the widget associated with the parameter. In a furtherembodiment, the regions that activate and deactivate the display of theparameter name and value may be different.

Parameter value viewer 122 can provide a right-click menu to the widgetthat displays the parameter and its value to allow a user to have theoption of making the widget selectively visible and hence displaying theparameter name and value at all times until the users indicatesotherwise. In FIG. 3D, hotspot 306 has a right-click menu 340 showingthree options: always visible, remove hotspot, and customize. In oneembodiment, by activating the always visible option, widget 326 isselectively displayed in the model window. An “x” may be provided at theupper right-hand corner of widget 326 once widget 326 is selectivelydisplayed so that a user can choose to make widget 326 disappear byselecting the “x” with a pointing device. In another embodiment, a usermay make widget 326 disappear to deselect the always visible option inthe right-click menu 340.

Once widget 326 is selectively displayed, widget 326 may be moved toother locations in the window displaying the executable block diagrammodel. In another embodiment, widget 326 may be moved to other windowsor dialogs associated with the executable block diagram model. In stillanother embodiment, widget 326 may be moved to the desktop or a windowof another application. By placing the cursor 302 over widget 326,repositioning icon 342 is displayed that allows a pointing device todrag or move widget 326 to other locations within the executable blockdiagram model. In another embodiment, when repositioning icon 342appears, a widget may be copy/cut from one location and pasted intoanother location. In one embodiment, widget 326 maintains a relativeposition with respect to the belonging block, in this case, block 300.

FIG. 3E illustrates how a block parameter and its value can be depictedusing an exemplary user interface widget other than text fields or comboboxes. Block 344 has a hotspot 346. When block 344 is selected, cursor302 may move into a region of hotspot 346 to trigger display of widget348. Widget 348 shows that a check box is used to indicate if a zerocrossing option is used in the algorithm for block 344.

FIG. 3F illustrates an exemplary embodiment where multiple userinterface widgets are associated with one hotspot, and these widgets areused to change a property of a block. Block 310 has a hotspot 312. Whena cursor 302 hovers over hotspot 312, widget 311 is displayed showingthat a property “limit output” of block 310 is off. When hotspot 312 isselected, widget 311 becomes editable and displays a check box optionfor a user to decide if the property “limit output” should be enabledfor block 310. If the check box in widget 311 is selected, a text field324 can appear to let a user specify the limits of the output.

In one embodiment, the upper limit and the lower limit shown in the textfield 324 may be changed by mouse movement, such as increasing a valueof the upper limit or the lower limit by moving the scroll wheel of amouse. In another embodiment, an input device, such as a stylus, may beused to draw a number that is adopted as the new parameter value.

FIG. 3G illustrates how a hotspot can be created in one exemplaryembodiment. Dialog window 330 (a separate window from the model window)shows the parameters of gain block 337, including “gain” parameter witha value of “1” as shown in text field 332, “multiplication” parameterwith a value of “Element-wise(K.*u)” in drop-down list 334, and “sampletime” parameter with a value of “−1” in the text field 336. To add ahotspot, a user can use the right-click menu of a parameter in thedialog window 330 and choose the option “Add as hotspot”. In theillustrative example, hotspot 331 is added to gain block 337 using theright click menu 338 of the sample time parameter. Hence, FIG. 3G showsthat a user can choose what parameters/properties of a block diagrammodeling component, such as a block, to expose as hotspots.

FIG. 3G further illustrates how a hotspot can be customized in oneexemplary embodiment. FIG. 3G shows that hotspot 331 has a right clickmenu widget 335 that provides a user with options to remove the hotspot331, make the hotspot 331 always visible, or customize the hotspot 331.A user may customize the look of hotspot 331 by choosing the customizeoption in the right click menu widget 335 of the hotspot 331. A user canalso customize or choose a hotkey for the hotspot using the customizeoption. Instead of a right click menu to provide a user the option tocustomize a hotspot, other means, such as one or more keystrokes, can beused to give the user the option to customize a hotspot.

FIG. 3H illustrates an exemplary user interface that may be used tochange the appearance and position of a hotspot. FIG. 3H shows thatblock 337 has a hotspot 331 that displays “sample time=−1” and has arectangular shape. A graphical user interface 339 may appear for a userto customize a hotspot 331 when a user selects a customization optionrelated to the hotspot 331, such as right-clicking with a mouse onhotspot 331 to get a right click menu 335 as shown in FIG. 3G.

In one embodiment, graphical user interface 339 may be a dialog box thatis displayed in a separate window from the model window. In anotherembodiment, graphical user interface 339 may be displayed in the samemodel window. Graphical user interface 339 includes a text field 354 forentering drawing commands for hotspot 331. Text field 354 has a MATLABcommand that outputs “sample time=” and the value of a variable with thename “sample_time”. The MATLAB command determines the text that isdisplayed in hotspot 331.

Graphical user interface 339 may include a check box 350 that allows auser to select if hotspot 331 should be always visible. Graphical userinterface 339 further includes a relative x position text field 358 anda relative y position text field 356 for customizing a relative location(in pixels) of the hotspot 331 with respect to its belonging block, i.e.block 337. The relative x position text field 358 shows a value of 0while the relative y position text field shows a value of −30. It isnoted that FIGS. 3H-3K are not drawn to scale. Graphical user interface339 includes a field 352 for customizing a keyboard shortcut, i.e. ahotkey, for selecting hotspot 331 from a keyboard when block 337 isselected. Field 352 may include one or more key strokes to be used as ahotkey.

FIG. 3I illustrates the use of an image to customize the appearance of ahotspot in one exemplary embodiment. In text field 354, a user can entera command to use an image to customize an appearance of a hotspot. Animage file with the name of “clock.gif” is used to customize theappearance of hotspot 331. Instead of using a command to output “sampletime=” and the value of the sample_time variable, a command is used tooutput “=” and the value of the sample_time variable. When apply button359 is selected by a pointing device, the appearance of hotspot 331 isupdated according to the new drawing commands in text field 354.

FIG. 3J illustrates how the shape and position of the hotspot may becustomized in one exemplary embodiment. Besides the drawing commandsshown in FIG. 3I, FIG. 3J further includes a shape command that sets theshape of hotspot 331 to an ellipse in the text field 354. The shapecommand changes the shape of the hotspot from a rectangular shape to anelliptical shape. The relative-y position field 356 is changed from itsprevious value of −30 to 50. Once the apply button 359 is selected, theshape and position of the hotspot is updated. Hotspot 331 is nowdisplayed below block 337 instead of above. Hotspot 331 also has anelliptical shape instead of rectangular shape.

FIG. 3K illustrates how a plot of a function can be used as theappearance of a hotspot in one exemplary embodiment. To change anappearance of the hotspot, one or more commands are used in the textfield 354. To plot a function, a MATLAB plot command may be used. InFIG. 3K, text field 354 shows that a function of sin(x) is used as aninput to a MATLAB plot command. Text field 354 further includes a shapecommand that specifies the shape of the hotspot to be a roundedrectangle. Text field 354 also includes a size command that specifiesthe size of the hotspot to be 80 pixels wide and 80 pixels high. Boththe relative x position text field 358 and the relative y position textfield 356 has a value of 0, which yields that the center of the hotspot331 is the same as the center of its belonging block, i.e. block 337. Inone embodiment, when a hotspot and its belonging block overlaps, thehotspot is displayed instead of the belonging block for the overlappingportion.

The present invention is not limited to the specific GUI widgetsillustrated or mentioned herein and any suitable GUI widget may be usedin the present invention for displaying and editing parameter values.

FIGS. 4A and 4B illustrate the use of an editable pop-up table to viewand edit block parameter values. When block 400 is selected, a widget402 appears and displays a list of parameters and their values. In FIGS.4A and 4B, widget 402 is shown as an editable pop-up table. Widget 402is a user interface widget associated with the same model window and noseparate window is needed to edit a parameter value. In an illustrativeembodiment, widget 402 disappears if cursor 302 moves away from a regionof block 400 that activates the display of a widget 402.

Widget 402 may have a pin button 418 that provides an always visibleoption that a user may select. Widget 402 may have a hyperlinked title416 that may provide a hyperlink to the documentation for block 400.Widget 402 shows in entry 404 an “input type” parameter with “vector” asits value. Entry 406 shows “input mode” parameter with the value being“one based.” Entry 408 shows that parameter “index as starting value”has the value “true.” Entry 410 indicates that the parameter “source ofelements index” is set to “Internal.” Widget 402 also has entry 412showing parameter “elements” having value “1” and entry 414 showingparameter “sample time” having value of “−1.” Each parameter in thewidget 402 may have an associated hotkey that is illustrated by thebolded letter corresponding to the hotkey in the parameter name. Hence,instead of using a pointing device, keystrokes can be used to select anentry in the widget 402 to start the editing of the associated parametervalue.

FIG. 4A shows that entry 404 includes a drop-down list for a user tochoose possible values for the parameter “input type.” FIG. 4B showsthat entry 414 includes a text field for a user to enter a value for theparameter “sample time.” Any graphical user interface elements, such as,a radio button, a combo box, a text field, a check box, can be used inan editable pop-up table, and the present invention is not limited tothe examples listed herein.

FIG. 4C illustrates the use of an exemplary user interface that does notuse a table to display block parameter values in one exemplaryembodiment. Widget 402 is shown as a pop-up that is not a table butstill displays various parameters of block 400. Widget 402 may includehyperlink title 416 that may link to a documentation of block 400. A pinbutton 418 may be provided as an always visible option that a user mayselect.

Widget 402 further includes input type parameter 420, input modeparameter 372, index as starting value parameter 424, source parameter376, elements parameter 428, and sample time parameter 430. Input typeparameter 420 has a combo box 432 that allows a user to select a desiredparameter value. Input mode parameter 372 and source parameter 376 haverespectively combo box 434 and combo box 438 for selecting a desiredparameter value. Index as starting value parameter 424 has a check box386 for selecting or deselecting the option of using index as startingvalue parameter 424. Elements parameter 428 and sample time parameter430 have respectively text field 440 and text field 442 for a user toenter a desired parameter value.

FIG. 5A illustrates a bar as the user interface widget that allowsviewing and editing of block parameter values. In another embodiment, abar 502 can be provided to view and edit parameter values when block 506is selected. Bar 502 can be displayed anywhere in the window 500. Bar502 shows “input type” parameter with “vector” as its value. Bar 502also shows “input mode” parameter with value as “one-base” and “sampletime” parameter with value as “−1.” Button 504 may be provided at an endof bar 502 to allow viewing of additional parameters and their values.To make bar 502 disappear, a user can select the “X” at one end of thebar 502. There are many different kinds of user interface widgets thatcan be used to view and/or edit parameter values in the same modelwindow so that no separate window, such as a dialog window, needs to beused.

FIG. 5B illustrates a search bar for locating a parameter having aspecific value. In one embodiment, a search tool may be provided in thestatus bar 508 of the window 500. Alternatively, the search tool may beprovided in a tool bar or other windows related widgets. The search toolcan provide search category option 516 for choosing a search category,such as configuration preferences, block names, or parameters. Eachcategory may be associated with a hotkey. For example, configurationpreferences may be associated with hotkey “c,” whereas block names andparameters are associated with hotkey “n” and “p,” respectively. Hence,instead of using a pointing device to choose a search category, a hotkeymay be used.

The search tool may provide a text field 518 for a user to enter a nameand/or a value of a configuration preference, block, a search category,or a parameter. Search results can be highlighted, such as by using abox 510, to show the block diagram modeling component(s) that matchesthe search results. FIG. 5C illustrates an alternative method fordisplaying search results.

FIG. 5C shows that a panel or user interface widget 512 is used to listsearch results. Widget 512 may have an “x” sign element 516 that isactivatable to make widget 512 disappear. FIG. 5D illustrates yetanother method for displaying search results by having search resultsdisplayed in the status panel 508 of window 500. A next button 514 maybe provided to view an additional result, for example one that does notfit in the status bar 508. One of ordinary skill in the art willappreciate that the present invention is not limited to the specific GUIwidgets illustrated or mentioned herein and any suitable GUI widget maybe used in the present invention for displaying and editing parametervalues.

FIG. 6A illustrates a flowchart depicting steps taken to display and/oredit a parameter value according to one embodiment. In step 602, anexecutable block diagram model 200 is displayed in a first window 500.In one embodiment, the executable block diagram model 200 is created ina time-based block diagram environment, such as a SIMULINK-compatibleenvironment.

In step 606, modeling environment 120 receives a first input from aninput device, where the first input associates with a first parameter ofa block diagram modeling component in the executable block diagram model200. In one embodiment, the first input may be from a pointing device112, where the first input is a selection of a hotspot 304-308associated with the first parameter. A selection may be made by having acursor 302 hovering over the hotspot 304-308 or having a pointing device112 clicking on the hotspot 304-308. In another embodiment, the firstinput may be from a keyboard 110, where the first input is a hotkeyassociated with the first parameter.

In still another embodiment, the first input may be a selection of ablock diagram modeling component, such as a signal 202-204. A selectionof the block diagram modeling component in the executable block diagrammodel 200 may be received in step 604. The user may enter a first inputassociating the block diagram modeling component with a first parameterin step 606. The first input may trigger a first user interface widget206-208 to be displayed in the model window (i.e. the first window). Inone embodiment, no additional window, such as a dialog, is needed toview and/or edit a value of a parameter. The first parameter isrepresented in the executable block diagram model 200 by a firstgraphical affordance. The first graphical affordance can be a hotspot304-308 or a block diagram modeling component in the executable blockdiagram model 200.

In step 608, a value of the first parameter may be displayed by aparameter value viewer 122 in the first user interface widget 206. Thevalue displayed in the first user interface widget 206 may be editable.The first user interface widget 206 may be always visible in theexecutable block diagram model 200. In one embodiment, the first userinterface widget 206 may be displayed in the vicinity of the firstgraphical affordance. In another embodiment, the first user interfacewidget 206 may be a bar displayed at a side of the first window.

In step 610, a history of values of the first parameter may beoptionally displayed in the first user interface widget 222. The historyof values may include simulation values, user-defined values, valuesfrom different simulation runs, etc. The first user interface widget 222is continuously updated with new simulation and/or execution values. Instep 612, simulation and/or execution values of the first parameter maybe optionally displayed in the first user interface widget 222 duringsimulation and/or execution of the executable block diagram model 200.Exemplary embodiments may provide a convenient and easy to use mechanismthat allows a user to view how a parameter value changes duringsimulation and/or execution of the executable block diagram model 200.

In step 614, the first user interface widget may be optionallyrepositioned with respect to the executable block diagram model 200 inthe first window according to a second input from an input device.Inputs from an input device, such as, a keyboard 110, a pointing device112, or a touchpad may be used to reposition the user interface widget.The first input and the second input may be received from differentinput devices. In step 616, the first user interface widget mayoptionally display a name of the first parameter.

FIG. 6B illustrates additional steps that may be taken alone or inaddition to the steps shown in FIG. 6A. In step 618, a cursor 322 may beoptionally displayed at the displayed value of the first parameter toallow editing of the first parameter value. In step 620, input may beoptionally received from the input device, where the input includes anew value for the first parameter. The first parameter value mayoptionally be changed to the new value in step 622 and the new value maythen be displayed in the first user interface widget 326 in step 624.

In step 626, the first graphical affordance associated with the firstparameter may optionally be updated in the executable block diagrammodel 200. In step 628, an associated hotkey of the first parameter oran appearance of the first user interface widget 337 may be optionallycustomized. In step 630, a name and a value of a second parameter mayoptionally be displayed in the first user interface widget 337. Thefirst user interface widget 337 may be an editable pop-up table.Alternatively, a second user interface widget may be used in the firstwindow to display the second parameter in step 632. The second parametermay be represented by a second graphical affordance in the executableblock diagram model. In one embodiment, the second parameter may have adifferent hotkey than the first parameter.

FIG. 7 illustrates a flowchart depicting steps taken to search for aparameter according to one embodiment. In step 700, an executable blockdiagram model 200 is displayed in the first window 500. In step 702, thesearch tool is displayed in a status bar 508 of the window 500, wherethe search tool includes a category option 516 and a text field 518 forreceiving a search string. In optional step 704, modeling environment120 may receive input specifying the search category. For example, theinput may be a hotkey associated with the search category. In step 706,the search string and a search category in the category option 516 maybe used to search the executable block diagram model 200.

In step 708, a search result may be displayed in the window 500. Thesearch result may be displayed by highlighting one or more block diagrammodeling components or one or more hotspots in the executable blockdiagram model 200. The search result may alternatively be displayed in apanel in the window 500. In another aspect, the search result may bedisplayed in a status bar 508. In step 710, a next button 514 may beoptionally provided in a status bar 508 to show additional search resultthat is not able to be displayed in the status bar 508. In oneembodiment, the status bar 508 shows one search result at a time, andthe next button 514 is used to browse through the list of searchresults. In another embodiment, a previous button, an end and beingbutton, and/or a button to move forward and backward by multiple resultsmay be provided.

FIG. 8A illustrates an exemplary executable block diagram model that isreferenced in FIGS. 8B to 8H for describing exemplary graphical userinterfaces for viewing specified levels of detail for a block diagrammodeling component. As a user browses/navigates in an executable blockdiagram model, different levels of detail of block diagram modelingcomponents may be displayed. Model 800 models an operation of anaircraft. In model 800, various blocks, such as blocks 804, 806, and808, model different aspects of the aircraft and data analysisfunctionality. A multi-level detail viewer may be used to browse model800 so that details of a block diagram modeling component can be viewed,for example, when lens cursor 802 is within a region that activates thedisplay of the details. In one embodiment, different types of blockdiagram modeling component may have different levels of detail anddifferent numbers of levels of details.

FIG. 8B illustrates an exemplary graphical user interface for viewingdifferent levels of detail of a block diagram modeling component. In oneembodiment, a lens-like widget 810 is displayed over block 804 when lenscursor 802 moves within a region that activates the display of lens-likewidget 810. Widget 810 may display three parameters: numeratorcoefficient 816 and its corresponding value, denominator coefficient 818and its corresponding value, absolute tolerance 820 and itscorresponding value. A user may modify the existing value of a parameterin the lens-like widget 810. Text fields 816, 818, and 820 are providedto allow a user to modify a value of numerator coefficient 817,denominator coefficient 819, and absolute tolerance 821, respectively.

A control panel 811 may be provided to let a user change propertiesrelated to lens-like widget 810. Control panel 811 includes a lens sizecontrol slider 812 and detail level control slider 814. Lens sizecontrol slider 812 enables a user to adjust the size (i.e. diameter) ofthe lens-like widget 810 while detail level control slider 814 enables auser to select a specific detail level of block 804 to display in thelens-like widget 810. Each block in an executable block diagram modelmay have different levels of details. For example, a block may have aparameter level showing details regarding the parameter values and agenerated code level showing details regarding the generated code fromthe block. Although exemplary embodiments are discussed with specificlevel of details, the invention is not limited to these specific levelsof details discussed herein. There may be other embodiments where usersmay configure the parameters to create a fisheye view using thelens-like widget 810.

FIG. 8C illustrates another exemplary graphical user interface forviewing different levels of detail of a block diagram modelingcomponent. Instead of using a lens-like widget 810, FIG. 8C shows that aviewer widget 830 is used to display the parameters and their values. Inone embodiment, viewer widget 830 may be displayed in the model window.In another embodiment, viewer widget 830 may be displayed in a separatewindow.

Viewer widget 830 includes a radio button 822 for selecting a parameterlevel of detail, a radio button 824 for selecting an algorithm level ofdetail, a radio button 826 for selecting a generated code level ofdetail. For each level of detail, specific information regarding a blockdiagram modeling component can be displayed. The parameter radio button822 is selected in FIG. 8C and hence, parameters, such as numeratorcoefficient 816 and its corresponding value, denominator coefficient 818and its corresponding value, absolute tolerance 820 and itscorresponding value are displayed in viewer widget 830. A user canmodify a value of numerator coefficient 817, denominator coefficient819, and absolute tolerance 821 via text fields 816, 818, and 820,respectively.

FIG. 8D illustrates details of an exemplary algorithm used with a blockdiagram modeling component. FIG. 8D shows that algorithm radio button824 is selected in viewer widget 830 instead of parameter radio button822. Accordingly, viewer widget 830 displays the algorithm level ofdetail for block 804 in display panel 828. An algorithm level of detailis associated with the algorithm that is used in the correspondingblock. In one embodiment, the algorithm may be shown using one or moreequations that relate the output(s) of the block with the input(s).

FIG. 8E illustrates exemplary generated code detail of a block diagrammodeling component. FIG. 8E shows that generated code radio button 826is selected in viewer widget 830. Details of generated code for block804 are displayed in display panel 829. One of ordinary skill in the artwill appreciate that although FIGS. 8C to 8E show three specific levelsof detail, the present invention is not limited to the specific levelsof detail discussed herein. In addition, different levels of detail maybe shown concurrently according to one embodiment.

FIG. 8F illustrates an exemplary graph level of detail of a blockdiagram modeling component. In one embodiment, when lens cursor 802moves within a region of block 806, viewer widget 840 may be displayedin the model window to show a specified level of detail. Block 806represents a scope where a user can review values of an input signal 805with respect to time. For block 806, two different levels of detailinstead of three are available for display in viewer widget 840. Viewerwidget 840 has a radio button 842 for selecting to show a graph detailand a radio button 844 for selecting to show a data detail in viewerwidget 840. In FIG. 8F, graph radio button 842 is selected and a graph846 is displayed in viewer widget 840.

FIG. 8G illustrates an exemplary data level of detail of a block diagrammodeling component. In FIG. 8G, data radio button 844 is selectedinstead of graph radio button 842 in viewer widget 840. Accordingly,viewer widget 840 displays data for the input signal 805 of block 806with respect to time. One of ordinary skill in the art will appreciatethat although FIGS. 8F to 8G show two specific levels of detail, thepresent invention is not limited to the specific levels of detaildiscussed herein.

FIG. 8H illustrates an exemplary subsystem detail of a block diagrammodeling component. In one embodiment, when lens cursor 802 moves withina region of block 808, viewer widget 850 is displayed to show details ofblock 808. In another embodiment, block 808 may be selected with thelens cursor 802 being active and cause the viewer widget 850 to displaythe details of block 808. Viewer widget 850 includes a radio button 852for selecting a parameter detail, a radio button 854 for selecting asubsystem detail, a radio button 856 for selecting a generated codedetail. In FIG. 8H, subsystem radio button 854 is selected. Accordingly,viewer widget 850 displays in panel 858 the block diagram modelingcomponents that made up the subsystem in block 808. One of ordinaryskill in the art will appreciate that although FIG. 8H shows threespecific levels of detail, the present invention is not limited to thespecific levels of detail discussed herein.

One of ordinary skill in the art will appreciate that although FIGS.8A-8H are discussed with exemplary GUI widgets, the present invention isnot limited to the exemplary GUI widgets described herein.

FIG. 9A illustrates an exemplary statechart that is referenced in FIGS.9B and 9C for describing how to model a two car elevator systemillustrating some of the common elements of modern elevators such ascall queuing, fire alarm responses, hall calls and the like. Thestatechart is created using Stateflow® of MathWorks Inc, of Natick Mass.and it illustrates a rich set of Stateflow® features such as the abilityto call MATLAB functions 914, embedded MATLAB 916, graphical functions918 and truth table blocks 912. In addition, it uses Stateflow®semantics such as parallel state decomposition, event broadcasts, innertransitions and the like. As a user browses/navigates in a statechart,different levels of detail of statechart components may be displayed.

FIGS. 9A and 9B illustrate exemplary graphical user interfaces forviewing different levels of detail of a statechart component. In oneembodiment as depicted in FIG. 9A, the magnification tool 908 is placedover a subchart 902 in Stateflow® chart 901. Placing the magnificationtool 908 over the subchart 902 enables a user to see into the subchart902 in the viewing window 910 at the bottom right of the Stateflow®environment 900. User is also presented with the option of seeing evendeeper into the subchart 902 by providing the option to see thegenerated code 930.

FIG. 9B illustrates a magnification lens 920 being placed over thesubchart 906 in Stateflow® chart 901. The magnification lens 920provides the user with a detailed view of the elements beneath theexterior block. A close-up view of block elements 930 is illustrated inFIG. 9C. A control panel 922 may be provided to let a user changeproperties related to lens-like widget 920. Control panel 922 includes alens size control slider 924 and magnification factor control slider926. Lens size control slider 924 enables a user to adjust the size(i.e. diameter) of lens-like widget 920 while magnification factorcontrol slider 926 enables a user to select a specific detail level ofblock 906 to display in the lens-like widget 920.

FIGS. 10A and 10B illustrate another exemplary use of lens cursor 802.FIG. 10A illustrates an exemplary detail of a composite signal. FIG. 10Ashows model 1000 that combines bus 1 (signal 1003) and bus 2 (signal1002) to create main bus (signal 1004) via a bus creator 1001. In oneembodiment, lens cursor 802 is placed on a bus to view details of a bus.FIG. 10A shows that lens cursor 802 is placed on bus 2 (signal 1002) andviewer widget 1010 is displayed to show a specified level of detail ofbus 2. Viewer widget 1010 has a radio button 1006 for selecting a busdetail and a radio button 1008 for selecting a generated code detail todisplay in viewer widget 1010. In FIG. 10A, radio button 1006 for busdetail is selected. Viewer widget 1010 shows that signal 1002 includesclock signal 1012, pulse signal 1014 and sine signal 1016.

FIG. 10B illustrates another exemplary detail of a composite signal. InFIG. 10B, lens cursor 802 is positioned on top of signal 1004 and busdetail radio button 1006 is still selected in viewer widget 1010.Accordingly, viewer widget 1010 shows that signal 1004 includes twobuses: bus 1 (signal 1003) and bus 2 (signal 1002), where bus 1 includeschirp signal 1018 and constant signal 1020 while bus 2 includes clocksignal 1012, pulse signal 1014 and sine signal 1016.

One of ordinary skill in the art will appreciate that although FIGS.10A-10B show two specific levels of detail, the present invention is notlimited to the specific levels of detail discussed herein. AlthoughFIGS. 10A-10B are discussed with exemplary GUI widgets, the presentinvention is not limited to the exemplary GUI widgets described herein.

In one embodiment, the use of different levels of details of a blockdiagram modeling component may help in identifying a problematic part ofa model. In one embodiment, an evaluation such as a check or test may berun on a model and one or more links may be provided to a level ofdetail that shows the problematic part of the model. In one embodiment,the problematic part of the model may be highlighted in the level ofdetail so that a user can easily identify the problematic part thatneeds to be fixed instead of searching through the model to determinewhat aspect of a block is problematic.

FIG. 11A illustrates an exemplary graphical user interface that may beused to find upgrade issues in an executable block diagram model.Graphical user interface 1100 is provided to let a user select differentkinds of checks that may be run against a model. Graphical userinterface 1100 includes an upgrade check 1102 that checks for commonupdate issues. A button 1104 is provided to start a check that isselected in graphical user interface 1100. Label 1108 provides adescription of the upgrade check 1102. Results of a check are displayedin text field 1106.

FIG. 11B illustrates exemplary results of running the check 1102illustrated in FIG. 11A. Text field 1106 may display recommended changesto the model to fix any problem. In another embodiment, text field 1106may also display recommended steps that a user should follow to find allthe possible problems in the model. Graphical user interface 1100 maydisplay a check box 1110 for allowing a user to ignore failure that wasfound after running a check. Text field 1106 may include a hyperlink1112 that provides a link to the part of the model that is identified asproblematic. By selecting hyperlink 1112 with a pointing device, a modeland a level of detail of the problematic block diagram modelingcomponent may be displayed, such as shown in FIG. 11C.

FIG. 11C illustrates how a level of detail may be displayed to show anexemplary issue that can be present in the executable block diagrammodel. FIG. 11C shows a model 1120 and a viewer widget 1130 thatdisplays a level of detail of block diagram modeling component 1114.Block diagram modeling component 1114 is highlighted by box 1116 in themodel 1120 so that a user can easily identify the location of the issueidentified by running check 1102 in FIG. 11B. Viewer widget 1130displays a radio button 1122 for selecting a parameter level of detail,a radio button 1124 for selecting an algorithm level of detail, and aradio button 1126 for selecting a generated code level of detail.

In FIG. 11C, radio button 1122 for selecting a parameter level of detailis selected and various parameters and their corresponding values aredisplayed in viewer widget 1130. Viewer widget 1130 displays port numberparameter 1128, icon display parameter 1132, output when disabledparameter 1134, and initial output parameter 1136. A warning pop-up 1138is displayed to show that the value of initial output parameter 1136should be set to empty. The message shown in the warning pop-up 1138 isconsistent, but may differ, with the message shown in text field 1106 ofgraphical user interface 1100 in FIG. 11B.

In one embodiment, when hyperlink 1112 is selected by a user using apointing device, viewer widget 1130 is automatically displayed in themodel window to show a user which parameter is causing a check to fail.More than one parameter may cause a check to fail and that data otherthan parameters, such as unconnected block inputs or outputs, improperblock usage, mismatch of port and signal names, crossing transitions ina state transition diagram, multiple writes to a data store, automaticinsertion of rate transitions, wrong uses of a mux block for creatingbuses, may also cause a check to fail.

FIG. 12 illustrates a flow chart depicting exemplary steps taken to usea multi-level detail viewer in one exemplary embodiment. In step 1202,an executable block diagram model 800 is displayed. In step 1204, theexecutable block diagram model 800 may be navigated using a multi-leveldetail viewer. In step 1206, a first level of detail of a block diagrammodeling component 804 in the executable block diagram model may bedisplayed when the block diagram modeling component 804 is selectedusing a cursor 802 or one or more keystrokes. In step 1208, the blockdiagram modeling component 804 may be displayed in its normal mode whenthe block diagram modeling component 804 is not selected. In step 1210,a parameter or setting of the block diagram modeling component 804 maybe modified in the displayed first level of detail. In step 1212, asecond level of detail may be displayed instead of the first level ofdetail when the second level of detail is selected to be used with themulti-level detail viewer.

Exemplary embodiments described herein may be implemented in a technicalcomputing environment (TCE). A TCE may include hardware and/or softwarebased logic that provides a computing environment that allows users toperform tasks related to disciplines, such as, but not limited to,mathematics, science, engineering, medicine, business, etc., moreefficiently than if the tasks were performed in another type ofcomputing environment, such as an environment that required the user todevelop code in a conventional programming language such as C++, C,Fortran, Pascal, etc.

In one implementation, a TCE may include a dynamically typed languagethat can be used to express problems and/or solutions in mathematicalnotations familiar to those of skill in the relevant arts. For example,a TCE may use an array as a basic element, where the array may notrequire dimensioning. In addition, a TCE may be adapted to performmatrix and/or vector formulations that can be used for data analysis,data visualization, application development, simulation, modeling,algorithm development, etc. These matrix and/or vector formulations maybe used in many areas, such as statistics, image processing, signalprocessing, control design, life sciences modeling, discrete eventanalysis and design, state based analysis and design, etc.

A TCE may further provide mathematical functions and/or graphical tools(e.g., for creating plots, surfaces, images, volumetric representations,etc.). In one implementation, a TCE may provide these functions and/ortools using toolboxes (e.g., toolboxes for signal processing, imageprocessing, data plotting, distributed processing, etc.). In anotherimplementation, a TCE may provide these functions as block sets. Instill another implementation, a TCE may provide these functions inanother way, such as via a library, etc., a TCE may be implemented as atext based environment, a graphically based environment, or another typeof environment, such as a hybrid environment that is both text andgraphically based.

A TCE may be implemented in a number of forms, such as a text-basedform, a graphically-based form, etc. For example, a TCE may beimplemented using one or more graphically-based products. For example, agraphically-based TCE, may be implemented using products such as, butnot limited to, Simulink®, Stateflow®, SimEvents™, etc., by TheMathWorks, Inc.; VisSim by Visual Solutions; LabView® by NationalInstruments; Dymola by Dynasim; Extend from Imagine That Inc.; SoftWIREby Measurement Computing; WiT by DALSA Coreco; VEE Pro or SystemVue byAgilent; System VIEW from Elanix, Vision Program Manager from PPTVision, Khoros from Khoral Research, Gedae by Gedae, Inc.; Scicos from(INRIA); Virtuoso from Cadence, Rational Rose from IBM, Rhopsody or Taufrom Telelogic; or aspects of a Unified Modeling Language (UML) or SysMLenvironment. The graphically-based TCE may support code generation,constraints generation, constraints checking, etc.

A TCE may further be implemented as a hybrid TCE that combines featuresof a text-based and graphically-based TCE. In one implementation, oneTCE may operate on top of the other TCE. For example, a text-based TCE(e.g., MATLAB) may operate as a foundation and a graphically-based TCE(e.g., Simulink) may operate on top of MATLAB and may take advantage oftext-based features (e.g., commands) to provide a user with a graphicaluser interface and graphical outputs (e.g., graphical displays for data,dashboards to monitor performance of generated code, etc.).

In an alternative embodiment, aspects of the invention may beimplemented in a language that is compatible with a product thatincludes a TCE, such as one or more of the above identified text-basedor graphically-based TCE's. For example, SIMULINK (a graphically-basedTCE) may be used to practice exemplary embodiments described herein. ASIMULINK-compatible modeling environment provides means (e.g., viahardware or software based logic) to use a SIMULINK model and/orfeatures in the SIMULINK-compatible modeling environment. For example, aSIMULINK-compatible modeling environment may provide hardware and/orsoftware based logic to interface with a SIMULINK model, to import orexport a SIMULINK model, to translate a SIMULINK model, to integrate aSIMULINK model, etc. Although exemplary embodiments may be describedrelative to a SIMULINK-compatible modeling environment, the presentinvention is not limited to these embodiments and may be applied toblock diagram modeling and/or computing tasks via other block diagrammodeling environments.

Many alterations and modifications may be made by those having ordinaryskill in the art without departing from the spirit and scope of theinvention. Therefore, it must be expressly understood that theillustrated embodiments have been shown only for the purposes of exampleand should not be taken as limiting the invention, which is defined bythe following claims. These claims are to be read as including what theyset forth literally and also those equivalent elements which areinsubstantially different, even though not identical in other respectsto what is shown and described in the above illustrations.

1. A computer readable medium holding computer executable instructionsfor displaying one or more attributes associated with one of one or moreblock diagram modeling components of an executable block diagram model,where at least one of the one or more attributes has one or moreattribute values, the medium comprising: instructions for displaying anexecutable block diagram model in a first window, the executable blockdiagram model comprising a first block diagram modeling component havinga first attribute; instructions for associating the first block diagrammodeling component with a first graphical affordance; instructions fordisplaying the first block diagram modeling component with the firstgraphical affordance; instructions for activating the first graphicalaffordance in response to a cursor being proximate to the graphicalaffordance; and instructions for displaying a first widget in responseto activating the first graphical affordance, the first widget fordisplaying a history of attribute values associated with the first blockdiagram modeling component.
 2. The medium of claim 1, furthercomprising: instructions for receiving a first input, wherein the firstinput is related to the first attribute; instructions for modifying theone or more attribute values of the first attribute based on the firstinput; instructions for updating information about the first blockdiagram modeling component of the executable block diagram model usingthe one or more attribute values of the first attribute; andinstructions for displaying the updated information in the first widgetof the first window.
 3. The medium of claim 1, further comprising:instructions for receiving a second input, the second input including anadditional attribute value for the first attribute; and instructions fordisplaying the additional attribute value for the first attribute in thefirst widget.
 4. The medium of claim 1, wherein the first attributecomprises a simulation result of the first block diagram modelingcomponent, a subsystem represented by the first block diagram modelingcomponent, a code associated with the first block diagram modelingcomponent, parameters of the first block diagram modeling component, ora representation of the first block diagram modeling component generatedvia a scripting language.
 5. The medium of claim 1, further comprising:instructions for displaying one or more attribute values of a secondattribute in the first window or in a second window, wherein the secondattribute is represented by a second graphical affordance in theexecutable block diagram model.
 6. The medium of claim 1, wherein thefirst graphical affordance is provided on the block diagram modelingcomponent or around the block diagram modeling component as a hotspotregion, the hotspot region being displayed without using a graphicalicon.
 7. The medium of claim 6, further comprising: instructions fordisplaying a first hotspot region associated with the first attribute, asecond hotspot region associated with a second attribute and a thirdhotspot region associated with a third attribute; instructions fordisplaying the one or more attribute values of the first attribute whenthe first hotspot region is selected by the cursor being proximate tothe first hotspot region; instructions for displaying one or moreattribute values of the second attribute when the second hotspot regionis selected by the cursor being proximate to the second hotspot region;and instructions for displaying one or more attribute values of thethird attribute when the third hotspot region is selected by the cursorbeing proximate to the third hotspot region.
 8. A computer readablemedium holding computer executable instructions for causing a computingdevice to display one or more attributes associated with one or moreblock diagram modeling components of an executable block diagram model,where at least one of the one or more attributes has one or moreattribute values, said medium comprising: instructions for displaying anexecutable block diagram model in a first window, where the executableblock diagram model comprises a first block diagram modeling componentthat includes a first attribute having one or more attribute values;instructions for identifying one or more hotspot regions around thefirst block diagram modeling component, where the instructions foridentifying comprise: instructions for associating one of the one ormore hotspot regions with the first attribute, and instructions forassociating another of the one or more hotspot regions with a secondattribute when a second attribute is associated with the first blockdiagram modeling component; instructions for receiving a first input forthe first attribute or the second attribute, where the first inputmodifies one or more attribute values of the first attribute or thesecond attribute; and instructions for displaying the one or moreattribute values associated with the first attribute or the one or moreattribute values associated with the second attribute via a first widgetin the first window, where the displaying provides updated informationabout the first block diagram modeling component or the executable blockdiagram model.
 9. The medium of claim 8, further comprising:instructions for receiving second input, the second input includingadditional attribute values for the first attribute; and instructionsfor displaying the additional attribute values of the first attribute inthe first widget.
 10. The medium of claim 9, wherein the displaying theadditional attribute values includes replacing the one or more attributevalues of the first attribute with the additional attribute values. 11.The medium of claim 8, wherein the first widget is selectively visibleon the executable block diagram model.
 12. The medium of claim 8,wherein the first widget displays dynamic data.
 13. The medium of claim9, wherein the first attribute comprises simulation results of the firstblock diagram modeling component, a subsystem represented by the firstblock diagram modeling component, a code associated with the first blockdiagram modeling component, parameters of the first block diagrammodeling component or representation of the first block diagram modelingcomponent generated via a scripting language.
 14. The medium of claim 8,wherein the one or more hotspot regions are displayed without using agraphical icon.
 15. The medium of claim 8, further comprising:instructions for displaying a first hotspot region associated with thefirst attribute, a second hotspot region associated with a secondattribute and a third hotspot region associated with a third attribute;instructions for displaying one or more attribute values of the firstattribute when the first hotspot region is selected; instructions fordisplaying one or more attribute values of the second attribute when thesecond hotspot region is selected; and instructions for displaying oneor more attribute values of the third attribute when the third hotspotregion is selected.
 16. A system for displaying one or more attributevalues of one or more attributes of a block diagram modeling componentin an executable block diagram model, the system comprising: a displaydevice that displays an executable block diagram model having one ormore block diagram modeling components in a window, wherein the one ormore block diagram modeling components have one or more attributes; amodel editor that associates the one or more block diagram modelingcomponents or regions around the one or more block diagram modelingcomponents with one or more graphical affordances; an attribute valueviewer that in response to activating the one or more graphicalaffordances in response to a cursor being proximate to the one or moregraphical affordances, displays a first widget for illustrating ahistory of attribute values of a first attribute associated with a firstblock diagram modeling component; an input device for entering input tomodify the one or more attribute values displayed on the first widget;and an updating logic that updates the display of the block diagram withthe input entered using the input device.
 17. The system of claim 16,wherein the first attribute comprises simulation results of the firstblock diagram modeling component, a subsystem associated with the firstblock diagram modeling component, a code associated with the first blockdiagram modeling component, parameters of the first block diagrammodeling component or representation of the block diagram modelingcomponent generated via a scripting language.
 18. The system of claim16, further comprising: a multi-level detail viewer for displaying aspecified level of detail of one of the one or more block diagrammodeling components in the executable block diagram model when the oneof the one or more block diagram modeling components is selected,wherein the one of the one or more block diagram modeling components isdisplayed in its normal viewing mode, when the one of the one or moreblock diagram modeling components is not selected.